I experience many problems since I use FTP plugin 1.3.1
Exception occurs while saving file to remote server and then file cannot be saved
to server.
I open file from ProjectViewer, with project base path like: sftp://myremoteserver/my/dir/
The edited file has its address like: sftp://@myremoteserver/my/dir/file.ext
I experienced these exceptions really often: impossible to edit a file with jEdit
on a remote server, each time I restart jEdit, only one save is possible. Other attempts
to save lead to exception.
Submitted | lauhub - 2016-01-21 18:24:33.700000 | Assigned | ezust |
---|---|---|---|
Priority | 5 | Labels | FTP ssh ProjectViewer |
Status | pending | Group | |
Resolution | fixed |
2016-01-21 18:58:50.462000 lauhub |
I also experience ConcurrentModificationException when reloading a file (e.g. pressing
twice the reload button).
jEdit-concurrent.log (1.9Kio) |
---|---|
2016-01-21 23:44:02.751000 ezust |
If you do not supply a username, then SFTP plugin looks for a connection described
by your hostname in the "config" file. Do you have a config file that defines what
that server is supposed to point to? If not, supplying a username might solve your
problem.
|
2016-01-23 10:51:21.813000 lauhub |
Yes, I use a ssh config file. And the error occurs after I load the file at least
once. Sometimes, the file gets saved correctly, but it generally fails on second or
third time.
|
2016-01-24 19:59:20.411000 ezust |
Ticket moved from /p/jedit/plugin-feature-requests/362/ |
2016-01-24 19:59:34.266000 ezust |
- **assigned_to**: Alan Ezust |
2016-01-25 15:32:52.674000 ezust |
So just to confirm, this problem is only related to ProjectViewer integration? I am unable to see this problem using the file system browser. |
2016-01-25 15:34:11.060000 ezust |
- **labels**: FTP, ssh --> FTP, ssh, ProjectViewer |
2016-01-26 23:14:30.387000 lauhub |
Yes, disabling project viewer seems to remove the problem.
|
2016-01-29 09:39:04.136000 lauhub |
Hi,
|
2016-01-29 16:33:55.452000 ezust |
- **status**: open --> closed-works-for-me |
2016-01-29 16:33:55.772000 ezust |
I can't reproduce your problem on my particular ssh server.
|
2016-02-06 19:08:39.849000 lauhub |
Hi again,
bug-disconnecting.log (1.0Mio) |
2016-02-06 21:10:54.484000 ezust |
Try specifying a backup directory and see if the problem goes away.
|
2016-02-07 11:55:57.224000 lauhub |
I set the backup directory this morning. Same error just occured once again.
bug-with-backup-dir-set.log (27.9Kio) screenshot-error-dialog.png (21.3Kio) |
2016-02-16 17:04:05.500000 lauhub |
Today, I experience a lot of problems of the same type.
|
2016-02-18 11:49:41.072000 lauhub |
I identified an issue in the FTP source code.
|
2016-02-18 19:11:12.046000 ezust |
ok, I fixed the toString() method, and I updated the version of FTP.jar on dropbox.
|
2016-02-18 19:11:41.183000 ezust |
- **status**: closed-works-for-me --> pending-fixed |
2016-02-19 08:54:35.413000 lauhub |
OK thanks a lot.
|
2016-02-19 10:34:32.271000 lauhub |
Some news (not good I am afraid) :(
NullPointerException.log (6.2Kio) |
2016-02-19 17:52:40.164000 ezust |
If you find other issues in our code, let me know. It seems your recent discussion
should go on the jsch-users@lists.sourceforge.net mailing list.
|
2016-02-19 17:57:04.011000 ezust |
If you find the permissions are reset by saving, you might want to switch off "two-stage
save" from global options - saving and backup. That is completely unrelated to this
ticket.
|
2016-02-19 17:59:13.422000 ezust |
Looking at the null pointer exception.log, it seems to be related to whether you have
some text selected or not! Very strange, and perhaps a bug in jEdit itself.
|
2016-02-26 10:59:06.655000 lauhub |
Ok, after some testing, it appears that the bug is still here.
|
2016-02-27 18:43:38.555000 ezust |
How do I reproduce this issue? Is it really the same issue as the one that is in the
initial description of this ticket? If not, perhaps this ticket should be closed and
a new one opened with a more descriptive title and steps to reproduce.
|
2016-02-28 12:25:43.993000 lauhub |
I agree. Opening a new bug may be the good solution.
|